CI: Enable BASH_EXEC checks in super-linter #3454
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
windows
|
I've been assigned this PR and the other one that I opened this weekend, but there's nothing that I can act upon. It's only missing to approve, and at least two of you passed through it. Was it something that you weren't directly comfortable with reviewing on the spot? What is expected for me to do with having it in my assigned PRs? |
neteler
approved these changes
Feb 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I also set the executable bits on the files that didn't have them and that failed the checks. I double checked the config.guess and config.sub files by checking out the git repo with
git clone https://git.savannah.gnu.org/git/config.git, both of them have the executable bit set there.